fix: explicitly set retries to 0 #715
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eliax1996
force-pushed
the
eliax1996/explicitly-set-producer-retries-to-0
branch
from
39f3201 to
64b6f3e
Compare
tvainika
previously requested changes
Sep 15, 2023
eliax1996
force-pushed
the
eliax1996/explicitly-set-producer-retries-to-0
branch
from
64b6f3e to
f9605df
Compare
|
Thanks for the catch @tvainika, don't know why I've committed it :) and also I don't know how I've deleted it :P |
tvainika
approved these changes
Sep 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently in the backup tool we leave implicitly the setting about the retries.
This (if the default value change) could lead to duplication of messages in the restore of a topic.